2.1.1. AgentView – Customer Structure: Enhanced Serial Number Search

Customer Structure in AgentView has been enhanced to improve usability when working with accounts containing a large number of subscriptions. Agents can now perform a full search on the primary serial number and build a dynamic list of subscriptions before applying actions from the right-click menu.

This reduces the need for manual scrolling, makes multi-selection clearer, and helps prevent errors by allowing agents to review their selection prior to applying actions. For further details, see Section 3.1.1.

2.1.2. Administration Console - Serial Number Management

A new Number Management option has been added to the Administration Console to support generation and maintenance of managed serial numbers, including allocating, deallocating, deleting and resetting of serial numbers, with an integrated error view. See Section 3.3.1 for details.

2.1.3. Business Configuration – Network Serial Numbers: Prefix/List Maintenance

Configuration Centre has been enhanced to allow prefix and list values to be added and maintained for network serial numbers via a new Prefixes/List option. For full detail, see Section 3.4.1.

2.1.4. Licensing Server

This CMP release introduces a Licensing Server which drives the modules and components that are installed. This allows the required components to be selected (including mandatory and optional modules), and a licence key to be generated for use during installation. The next release of CMP will enhance the server functionality further by controlling access to modules and components in real-time.

As part of this change, the Installation Configuration Tool (ICT) has been updated to accept the location of the generated .p12 certificate (on the Ansible control node) and the associated keystore password, which are required during deployment.

For deployment details and ICT configuration requirements, see Section 6.2.1.

2.2.1. AgentView – Orders: Product Catalogue Integration

The AgentView order panels have been refactored to integrate further with the Product Catalogue. As part of this change, product selection is now based on product offerings, with bundles represented as bundled product offerings, removing the dependency on product items within the order panels.

The products mini/bottom panels have been replaced with new product offering panels, the order header pricing now calculates from product offering pricing, and the order status actions have been simplified. For full details, see Section 3.1.2.

2.2.2. Administration Console – Network Requests: Manual update for stuck network actions

The Network Requests list view has been enhanced to allow back-office users to manually update network actions that are stuck in a pending status. This provides a controlled alternative to manual database updates and allows the subscription to be released from “activity pending” so actions can be retried if required. See Section 3.3.2 for details.

3.1.1. Customer Structure – Serial Number Search and Selection List

The Customer Structure screen in AgentView has been enhanced to make it easier to locate and work with subscriptions in large hierarchies. Agents can now search by the primary serial number and build a list of subscriptions before applying actions.

• A new search component is available at the top right of the Customer Structure panel allowing users to search the structure using serial number id 1.
• Matched subscriptions are highlighted in the hierarchy and automatically added to the scrollable selection list.
• Subscriptions selected directly in the hierarchy (including multi-selected subscriptions using CTRL) are also added to the selection list.
• The selection list supports clearing individual entries or clearing the full list, and is reset when leaving the Customer Structure.
• Right-click actions can be applied to the selected subscriptions once the selection is completed and has been reviewed; options that require a single selection remain disabled when multiple subscriptions are selected.

3.1.2. Orders – Product Catalogue Integration (Product Offerings)

The AgentView order panels have been refactored to integrate further with the Product Catalogue. Ordering and display of ordered items is now based on product offerings, with bundles represented as bundled product offerings.

Product offering panels

The existing products mini and bottom panels have been replaced with new product offering panels. These panels provide a consistent view of the product offering the order was for, and include a single right-click option: View which displays further details of the product offering and any product offering attributes.

• Mini panel shows: Product Offering Name, Quantity, Offering Price, Upfront Price, Instalment Price.
• Bottom panel shows: Offering Id, Product Offering Name, Type of Product, Quantity, Offering Price, Contract Term, Upfront Price, Instalment Price, Bundle.

Order header updates

• The gross price on the order header panel is calculated based on product offering pricing.
• The order status hyperlink options have been simplified to: Cancel Order and Resubmit Order.

Order comments panel improvements

The order comments panel has been improved to ensure no unnecessary text wrapping when entering and viewing order comments.

3.3.1. Serial Number Management

The Administration Console has been enhanced with a new Number Management option to support additional managed serial number maintenance operations. This complements the existing managed number processing by providing user-driven actions such as loading ranges of serial numbers, that are then executed via the managed number load job.

• Generate Serial Numbers - create sequential serial numbers for a selected network and serial number id, with optional reservation and allocation details.
• Manage Serial Numbers - search and select serial numbers, then perform bulk actions:
  • Allocate (to a salesperson or account)
  • Deallocate (back to not allocated)
  • Delete (physical delete from serial number management)
  • Reset (from selecting/cooling off/expired back to an allocatable state)
• View Serial Number Errors - view errors produced during serial number management activity and filter by network, serial number id and full/partial serial number.

All load and update activity is processed through the managed number load job, which has been refactored to support the additional execution paths (load, allocate, deallocate, delete and reset) and to record validation errors where requests are not compatible with the current management status.

3.3.2. Network Requests – Update Network Action Manually

A new Update option has been added to the Network Requests Log list view to support resolution of actions that are stuck at a status of 'Sent to Network'. This provides a controlled alternative to manual database updates by allowing an operator to progress the underlying action to an error outcome so the subscription is no longer blocked.

In practice, an operator will have the affected subscription number as well as the Actioned Item Number and the action type (all available in AgentView during initial troubleshooting). The subscription number can be used to search and locate the relevant Network Requests Log entries in the Network Requests list. The action type is also shown in the list view, allowing the operator to narrow the results to the specific action that is stuck.

• The Subscription column has been moved to the start of the list view.
• The subscription number search component has been repositioned above the Subscription column.
• The Update button is only available for unprocessed Network Requests where the underlying actioned item is in Sent to Network status. Selecting Update allows the operator to enter a comment; confirming the panel then creates a record in the Confirm Action Item Request table.

The Action Monitor job automatically processes this request and updates the relevant event and action statuses, allowing the subscription to be released from “activity pending” and enabling actions to be retried if required.

3.3.3. Serial Number Management – Management Status Label Update

The management status description Allocated to Dealer has been renamed to Allocated to Salesperson. This change applies wherever serial number management statuses are displayed.

3.4.1. Auto Timeout

An auto timeout capability has been implemented for the Aurora Console, aligning session behaviour with other CMP consoles. The timeout value matches the configuration used by the Administration Console.

3.5.1. Network Serial Numbers – Prefix/List Maintenance

New functionality has been introduced in Business Configuration to allow prefix or list values to be added and maintained for serial numbers. Note: Prefixes can be defined for both managed and non-managed numbers, but list values can only be defined for non-managed numbers.

• A new Prefixes/List button is available on the Network Serial Numbers list view. Selecting this opens a list view with the following columns:
  • Value (prefix or list value)
  • Description
  • Type (Prefix / List / None)
  • Min Length
  • Max Length
• The Prefixes/List list view supports Add, Edit, and Delete.
• For non-managed numbers, the ability to define prefix/list values is controlled by the Validation Type of the non-managed number (i.e. Prefix or List). If Validation Type is set to None, an error message is displayed if the user selects Prefixes/List.

3.5.2. Resource Templates – Resource Attribute Validation

Additional validation has been added to the Resource Template and Resource Attribute panels to protect templates that are already in use. Once a resource template has been associated with a product, it is no longer possible to add, edit, or delete the attributes of that template, and the UI will indicate why the change is not permitted. Standalone templates remain fully editable.

3.8.1. TMF Product Ordering – Orders By Account

The Get Product Order List API has been enhanced to support filtering by account number. This allows consumers to query for a list of product orders associated with a specific account.

3.7.2. Create Order – Package Products (Bolt-ons via Product Offerings)

The Create Order REST APIs have been enhanced to support ordering prepaid and postpaid bolt-on packages, either as standalone offerings or as part of a bundled product offering.

This change enables channels such as the MDS Webshop to order prepaid plans that include allowances by defining a bundle containing a prepaid price plan plus a prepaid (recurring) bolt-on. The constituent offerings within the bundle can be configured as not sellable individually in the Product Catalogue.

• Orders for bolt-on packages now trigger purchase bolt-on processing, introducing a link between orders and purchases. For prepaid scenarios, prepayments are linked to orders via purchases (there is no direct order-to-payment link).
• A CMP Payment Identifier (prepayment) can be supplied when ordering hardware or prepaid bolt-on packages.
• The Purchases API supports:
  • CMP Order Identifier + CMP Payment Identifier when hardware is ordered and prepaid, or when a bolt-on is ordered and prepaid.
  • CMP Order Identifier (without payment identifier) when a bolt-on is ordered and postpaid.
• Bolt-on ordering supports one or many subscription numbers:
  • If no subscription numbers are provided, the order can create new subscriptions via existing order logic and apply the bolt-on via a purchase.
  • If subscription numbers are provided, the order can process upgrades via existing order logic and apply the bolt-on via a purchase.

3.8.3. Create Subscription Order – Serial Number Products (Product Offerings)

The Create Subscription Order REST functionality has been extended to provide a complete solution for ordering serial number products via product offerings.

Serial number products can now be configured with or without an associated warehouse, which determines when the serial number is applied to the subscription (and therefore which activation type is used).

• No warehouse: the serial number is applied as a changing number at order creation time and the activation type is Immediate.
• Warehouse associated: an order request is generated for the warehouse and the serial number is applied as a changing number at Order Dispatch or Customer Activation time (based on the activation type).

Managed serial numbers

• Where the product offering attributes specify criteria for a managed serial number, the selection process validates that the number is eligible (including management status and allocation rules), and updates the managed serial number status to reflect it as selected.
• If a valid serial number cannot be selected, the order is moved to an Error state.

Number change rules and event processing

• A valid Number Change Rule is required for the serial number(s) being ordered. If no applicable rule exists, the order is moved to an Error state.
• When multiple serial number products exist in an order, a single number change event is generated for the collection of serial numbers (not one per product), and is processed according to the activation precedence rule: Immediate is trumped by Order Dispatch, which is trumped by Customer Activation.
• Where a price plan and one or more serial number products are ordered together, the order generates a Tariff Change or Connection event (depending on whether a subscription is associated with the order). In this case, a number change event is not generated and the event is processed using the same activation precedence rule once all serial numbers have been applied as changing numbers.

If multiple serial numbers require Customer Activation, they can be supplied together in a single Activate Subscription REST request.

3.9.1. CXP Extract - Invoice Line SERVICE_TYPE Description

In the invoice_line.dat extract file produced for CXP, the SERVICE_TYPE column is now populated with the service code description, rather than the service group code description.